home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d21
/
qemm1289.arc
/
QEMM1210.MSG
< prev
next >
Wrap
Internet Message Format
|
1989-12-18
|
7KB
From: Steven White Area: DESQview
To: Brice Fleckenstein 01 Dec 89 20:48:00
Subject: PERSTOR PS180 CONTROLLER AND QEMM
* Err: Date (file 66-Dec09.1 on 1:17/38.0, from 1:267/54.0)
Brice, Thanks... I understand now. The board I'm on told me there was mail
for me, and I guess there's no way of knowing whether it was to me or not.
There should be! Steven White
--- TPBoard 6.0
* Origin: The Final Frontier 9600 HST (518) 761-0869 (1:267/54)
SEEN-BY: 1/217 17/38 19/3 104/312 105/3 10 41 42 103 469 496
SEEN-BY: 124/1113 2122 2124 3207 4115 4210 4216 5211 6125 130/12
SEEN-BY: 134/1 103 147/7 20 46 170/400 265/7 343/300 351/199 1106
SEEN-BY: 387/5 388/5 390/1 392/9 395/3 396/1 911/5
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Johannes Hoerhan Area: DESQview
To: Chris Martinic 05 Dec 89 20:24:00
Subject: Problems with DV2.25
> Another Question: (on behalf of a friend who just bought DV386.)
> Everything works fine except that he can't access the floppies. If he
> even does a DIR on a floppy, the system hangs. The system hangs if a
> program uses a floppy too. (yes, the uses floppy option is set to on).
> HIS equipment: 386/387, VGA and multisync monitor, with video seven
> card, 2Mb ram, Award BIOS, Osborne machine. 1.2 Mb flop (5 1/4"), 1.44
> Mb flop (3 1/2") flop.
I had just the same problem and I spent a lot of time to solve that problem.
After, I do not know, how many tests and questions, I came to the conclusion
that this is not real a bug of DV but QEMM. Qemm influences INT 13 and in
combination with a Award Bios you got the well known result: The machine
locks up when you try to access the floppies.
I tried to load qext.sys before qemm and this helped with the Versions
up to DV 2.22. But when I got 2.25 I had the same troubles again.
At last I found the solution which works for me: I load QEMM with the
commandline option IGNOREA20 (IA is the shortcut) and it works good for me.
DEVICE=C:\386\QEMM.SYS ON MA=4 HA=16 RAM ROM IA NS
This is my line for qemm. Hope I could help your friend...
Hannes
--- FD 2.00
* Origin: BLUMENKISTL [HST] .................Vienna/Austria(2:310/10)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: BRUCE TINOCO Area: DESQview
To: CHARLES MARTIN 05 Dec 89 21:52:46
Subject: RE: DESQVIEW ON AN XT...
BT >then choose "BIOS calls used for Writes"
CM >I use Telix on a 386. After reading your message, I reconfigured
CM >TElix to this option. Now the screen is slower. Is there an
CM >advantage for 386's? Thanks.
Charles, on a 386 you will get better performance setting Telix to
"Direct writes to the screen" instead of "BIOS calls". Desqview used
with QEMM-386 has the ability to virtualize the screen on a 386
computer. This ability to manage the screen of a direct write
program makes it unnessary to configure for BIOS calls.
Just set the following items in the DV "Change Program" screen:
Writes text directly to screen.......: [Y]
Virtualize text/graphics (Y,N,T).....: [Y]
In the original message you saw, I suggested that an XT (or AT) user
try the BIOS calls to avoid bleed-thru into other Desqview windows.
You should not get bleed-thru on a 386!
-Bruce-
--- D'Bridge 1.21
* Origin: TechTalk BBS, Titusville,FL 407-269-5188 (4-hst's) (1:374/1)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Paul Marwick Area: DESQview
To: All 06 Dec 89 20:50:42
Subject: VGA and DESQview screen blanking
I've just installed a clone VGA card (Trident MicroSystems BIOS, no idea as to
the chipset used). Prior to installing it, I tried all the testing I could
think of - seemed to pass all the compatability tests pretty well.
Now I've got a problem. Its working fine, except for one thing - several
programs are defeating the DESQview screen blanker, and bringing the screen
back to life. I've noticed it happen when a caller exits from the BBS, or
when a caller exits from one of the online games. Once its been brought back
up like that, it doesn't blank again afterwards.
Anybody encountered similar problems? Better yet, has anyone got any ideas as
to fixes? I've tried a number of excludes and includes on the QEMM command
line, I've tried setting the VGA card to 8-bit mode instead of 16-bit... In
fact, I've tried everything I can think of to overcome it, so far without any
success.
Paul.
--- msged 1.999
* Origin: Marwick's MadHouse - Brisbane, Australia (3:640/820)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Chris Martinic Area: DESQview
To: Keith Conover 07 Dec 89 16:14:42
Subject: Re: Problems with DV2.25
Keith, Thanks for your input. However, a 286/ACC can't run QEMM.
I'm running QEXT which is just for loading DV. The expanded mem
manager for the ACC is ALLEMM4 which is all-computers own driver.
regards Chris.
--- Opus-CBCS 1.10.18a
* Origin: Software Tools - You'll Never WOC Alone, Sydney OZ) (3:711/403.0)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-
From: Brice Fleckenstein Area: DESQview
To: Ken Hendrickson 05 Dec 89 17:16:14
Subject: MULTITASKING
The key to your problem is that 640K - Desqview and LIM/EEMS needs to have as
LITTLE motherboard memory as possible, as the base 640K is where the EEMS/LIM
memory has to swap INTO.
There are a few possible cures:
(1) Disable all but 256K of your motherboard memory (this isn't possible on
ALL '286 machines, unfortunately).
(2) Get an All Charge Card and let that re-map ALL of your memory as
EEMS/Full LIM4 RAM.
(3) Upgrade to a '386 machine with QEMM.
If your motherboard will run with LESS than 256K onboard, then 1 is the
"optimum" solution for you. If your motherboard HAS to have 512K or more to
run, then 2 or 3 would be the "optimal" solution.
--- SFBHQ TBBS
* Origin: SFB HeadQuarters TBBS/DDOS/Bink Indy IN (317-636-5036) (1:231/190)
-*-*-*-*-*-*-*-*-*-*= DVNet Extracts =-*-*-*-*-*-*-*-*-*-*-